-
Notifications
You must be signed in to change notification settings - Fork 123
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Combine common code from vulkan capture manager and vulkan state writer #1841
Combine common code from vulkan capture manager and vulkan state writer #1841
Conversation
CI gfxreconstruct build queued with queue ID 289791. |
CI gfxreconstruct build # 5221 running. |
1782d9b
to
5702885
Compare
CI gfxreconstruct build queued with queue ID 289807. |
CI gfxreconstruct build # 5222 running. |
CI gfxreconstruct build # 5222 passed. |
5702885
to
79d91a3
Compare
CI gfxreconstruct build queued with queue ID 289895. |
CI gfxreconstruct build # 5224 running. |
CI gfxreconstruct build # 5224 passed. |
#endif | ||
} | ||
|
||
static void CommonWriteFillMemoryCmd(format::HandleId memory_id, |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think it would be better if instead of defining this function to pass the pointer to Writer's/Manager's WriteFillMemoryCmd
as an additional argument to CommonProcessHardwareBuffer
. But this would require writing a declaration for that function pointer somewhere that is common to all managers and is api agnostic since this function is referred to from a lot of places (dx12 capture manager, vulkan capture manager and state writer, and the page guard manager).
I think this gets outside of the scope of this PR so I'll just leave this here as a suggestion for a different PR.
CI gfxreconstruct build queued with queue ID 292515. |
CI gfxreconstruct build # 5259 running. |
CI gfxreconstruct build # 5259 passed. |
This is needed for #1812